; there are
2 tests failing in geolocation which shouldn't and 3 in contacts.
Device-motion is more severe and is breaking the entire test suite on WP. I
can start looking into those.
3) I'm not sure how to make the PRs to mobile-spec for removing tests
without requiring them to be merged in a specific
,
and geolocation on top of existing automated tests, which I did not
change.
I just tested those automated tests and they are breaking on WP; there
are
2 tests failing in geolocation which shouldn't and 3 in contacts.
Device-motion is more severe and is breaking the entire test suite on
WP. I
can
Done, but didn't test on wp.
On Wed, Aug 6, 2014 at 2:22 PM, Jesse purplecabb...@gmail.com wrote:
yes, or even #?back
@purplecabbage
risingj.com
On Wed, Aug 6, 2014 at 11:07 AM, Andrew Grieve agri...@chromium.org
wrote:
On Fri, Aug 1, 2014 at 1:19 PM, Staci Cooper staci@gmail.com
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-mobile-spec/pull/58#issuecomment-51418072
is this still valid? with everything moved to plugin tests ...
merge conflicts.
---
If your project is set up for it, you can reply to this email
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-mobile-spec/pull/16#issuecomment-51418146
is this still valid? with everything moved to plugin tests ...
merge conflicts.
---
If your project is set up for it, you can reply to this email
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-mobile-spec/pull/6#issuecomment-51418167
is this still valid? with everything moved to plugin tests ...
merge conflicts.
---
If your project is set up for it, you can reply to this email
Github user stacic commented on the pull request:
https://github.com/apache/cordova-plugin-contacts/pull/33#issuecomment-51077076
Tests removed from mobile-spec here:
https://github.com/apache/cordova-mobile-spec/pull/90
---
If your project is set up for it, you can reply to this
Github user stacic commented on the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/16#issuecomment-51078873
Mobile-spec tests removed here:
https://github.com/apache/cordova-mobile-spec/pull/95
---
If your project is set up for it, you can reply to this
Hey Michal,
I've followed up your instructions to easily integrate the test along with
plugin-test-framework, as you can see I have spammed a little bit the dev
list with PRs, anyway here's the list of PRs, that includes File, Media,
Battery-Status and Vibration:
https://github.com/apache/cordova
of existing automated tests, which I did not change.
I just tested those automated tests and they are breaking on WP; there are
2 tests failing in geolocation which shouldn't and 3 in contacts.
Device-motion is more severe and is breaking the entire test suite on WP. I
can start looking into those.
3
change. I'm happy to revert / would love a fix if you have
easy access to test on windows phone.
2) My pull requests include the manual tests for contacts, device-motion,
and geolocation on top of existing automated tests, which I did not change.
I just tested those automated tests
failing in geolocation which shouldn't and 3 in contacts.
Device-motion is more severe and is breaking the entire test suite on WP. I
can start looking into those.
3) I'm not sure how to make the PRs to mobile-spec for removing tests
without requiring them to be merged in a specific order
notes:
- The PR's have created a test folder, but I had written scripts to
expect tests folder. Its easy to change or just accept both, but I
wonder if we should settle on a single convention. Total bikeshed topic,
so I'll just pick one.
- PR's for new tests seem to be well isolated from each
Things to help move this along:
- Move test directories to tests and add nested plugin.xml, that would be
a great. You can look at an example here:
https://github.com/apache/cordova-plugin-device/tree/master/tests
- Test the PR locally by running the mobilespec create script to make sure
Sounds good, I'll get started.
On Wed, Jul 30, 2014 at 11:33 AM, Michal Mocny mmo...@chromium.org wrote:
Things to help move this along:
- Move test directories to tests and add nested plugin.xml, that would be
a great. You can look at an example here:
https://github.com/apache/cordova
ripping out huge portions of mobile spec, which is what I'm doing
now.
Few notes:
- The PR's have created a test folder, but I had written scripts to
expect tests folder. Its easy to change or just accept both, but I
wonder if we should settle on a single convention. Total bikeshed topic,
so I'll just
It would be great if someone with a Gingerbread device could run the
cdvtests for my pull request. [1]
On BB10 Blobs are BlobConstructor objects. With the previous check, the
test failed as unsupported even though it does pass when allowed to run [2]
I'd feel better knowing this still works
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-plugin-contacts/pull/33
CB-7148 Ported contacts tests to plugin-test-framework
Removed js-module from plugin.xml and added manual tests. Can someone
please merge this into cdvtest and then merge cdvtest
Hi all,
Several of us at IBM have been working on porting tests from mobile-spec to
the plugin-test-framework. I believe we have pull requests out for all of
the automated tests; we also have the manual tests ported and are just
wrapping up testing on ios/android, so those additional pull
can just switch the start page with no change to
committers.
Thanks for your work here!
-Michal
On Wed, Jul 16, 2014 at 4:38 PM, Staci Cooper staci@gmail.com wrote:
Hi all,
Several of us at IBM have been working on porting tests from mobile-spec to
the plugin-test-framework. I believe we
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-mobile-spec/pull/71
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user schettino72 opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/80
Fix CB-7115: Add manual test for events volumedownbutton / volumeupbutto...
...n
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Great!!
2014-07-08 10:55 GMT-05:00 Michal Mocny mmo...@chromium.org:
FYI filed ticket with INFRA to create cordova-plugin-test-framework:
https://issues.apache.org/jira/browse/INFRA-8017
On Tue, Jun 24, 2014 at 8:22 PM, Andrew Grieve agri...@chromium.org
wrote:
On Tue, Jun 24, 2014
Hi guys, just want to let you know that after recent update of one of our test
dependencies [1] you can see the following error when running 'npm test' (if
you did 'npm update' or installed everything from scratch)
jasmineNode.TeamcityReporter.prototype = new jasmine.TeamcityReporter
the older version with -g
npm install -g jasmine-node@1.14.1
On Thu, Jul 3, 2014 at 10:09 AM, Sergey Grebnov (Akvelon)
v-seg...@microsoft.com wrote:
Hi guys, just want to let you know that after recent update of one of our
test dependencies [1] you can see the following error when running 'npm
test
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-lib/pull/50
CB-7056 serve: fix Android test, make tests conditional
Fix **Android** merges codepath, as it turns out that merges
doesn't need the platform specific hack.
Adding **BlackBerry 10
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/50
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
/
/js-module
+
+ js-module src=test/tests.js name=tests
--- End diff --
As discussed on ML, the cdvtest branches should be deleted and tests to be
done on master. Going to close out this PR, but please make a new one with test
on master.
---
If your project is set up
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-camera/pull/34
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-network-information/pull/11
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-lib/pull/45
enable basic serve test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jsoref/cordova-lib cb_7042
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/45
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
I'm seeing 502 responses from cordova-filetransfer.jitsu.com, the instance
that we use for testing file-transfer, so I can't properly test a couple of
pull requests.
Who manages that machine, and can they see what's up with it?
(The error I see if I navigate there in a browser is Reached max
Just sent you the creds through private email.
On Friday, June 27, 2014, Ian Clelland iclell...@chromium.org wrote:
I'm seeing 502 responses from cordova-filetransfer.jitsu.com, the instance
that we use for testing file-transfer, so I can't properly test a couple of
pull requests.
Who
that we use for testing file-transfer, so I can't properly test a couple
of
pull requests.
Who manages that machine, and can they see what's up with it?
(The error I see if I navigate there in a browser is Reached max retries
limit; it doesn't sounds like a quota issue; could
wrote:
Just sent you the creds through private email.
On Friday, June 27, 2014, Ian Clelland iclell...@chromium.org wrote:
I'm seeing 502 responses from cordova-filetransfer.jitsu.com, the
instance
that we use for testing file-transfer, so I can't properly test a
couple of
pull requests
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-blackberry/pull/165
CB-7036 make npm test work again (using grunt instead of jake)
Apparently there used to be support for `npm test`,
it's been broken for a while because `cordova-blackberry` switched
Github user dylin commented on the pull request:
https://github.com/apache/cordova-blackberry/pull/165#issuecomment-47268188
r+
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-blackberry/pull/165
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
flag is present it
would copy the test files.
- 'cordova build' it would save a copy of config.xml or modify the file to
replace the content tag: 'content src=index.html /' by content
src=cdvtests/index.html /, as well as modify plugin.xml of each
installed plugin to add this tag: 'js-module src=test
run/emulate --tests' workflow.
Workflow:
- 'cordova prepare' has to change, only if the --tests flag is present it
would copy the test files.
- 'cordova build' it would save a copy of config.xml or modify the file to
replace the content tag: 'content src=index.html /' by content
src=cdvtests
GitHub user javierbb31 opened a pull request:
https://github.com/apache/cordova-plugin-network-information/pull/11
Port network tests to plugin-test-framework
Ported test from mobile-spec (which are written in jasmine 1.3) in
jasmine 2.0.
Added:
New js-module named
Github user javierbb31 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-camera/pull/34#discussion_r14040361
--- Diff: plugin.xml ---
@@ -202,6 +205,7 @@
!-- windows8 --
platform name=windows8
+dependency
GitHub user javierbb31 opened a pull request:
https://github.com/apache/cordova-plugin-camera/pull/34
CB- 6958. Port camera test to plugin-test-framework
Ported tests from mobile-spec (which are written in jasmine 1.3) in
jasmine 2.0.
Added:
New js-module named tests
/
/js-module
+
+ js-module src=test/tests.js name=tests
--- End diff --
Doesn't this mean that the tests are going to be added to every project
that uses this plugin?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user purplecabbage commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-camera/pull/34#discussion_r13982279
--- Diff: plugin.xml ---
@@ -202,6 +205,7 @@
!-- windows8 --
platform name=windows8
+dependency
Github user javierbb31 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-camera/pull/34#discussion_r13983869
--- Diff: plugin.xml ---
@@ -202,6 +205,7 @@
!-- windows8 --
platform name=windows8
+dependency
/
/js-module
+
+ js-module src=test/tests.js name=tests
--- End diff --
Yes, it means that the tests are going to be added on every project that
uses this plugin, however, this PR it should have to be addressed to another
branch(cdvtest, as it is for the plugin
Sorry I missed providing feedback on this earlier ...
Having a deeper look at this, I am not feeling great about the extra
requirement that every plugin have an additional branch.
Several concerns arise :
- test branch can be out of sync with master
- how do we test a specific version?
- tests
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/34#issuecomment-46609974
I've started a conversation on this, before we go and create `test`
branches for all ~20ish plugins.
http://markmail.org/message/576yxsj6xvg6rycw
on the
feature.
Jesse, I'm not seeing the benefit of using plugins-tests.xml or the
dependency on the test plugin yet, may you elaborate your thoughts?
My hope was that tests are just always installed alongside plugins. If
that is not a good idea for some particular plugin, say because it uses
huge assets, I
to
including the test framework + all the tests because they get loaded and
processed with all of the plugins and will impact load time even if never
run.
99.9% of the time the plugin tests will be used by us the plugin
developers, and not the people who use the plugin in there apps.
I agree, having
tests, we basically need to iterate all plugins looking for a
nested tests/plugin.xml, and install those. This can be added to
CLI/Plugman, or just be a CLI hook even.
(b) add a js-test-module or js-module type=test that is only used if
you run prepare with --test. Similar to the above, but I think
a js-test-module or js-module type=test that is only used if
you run prepare with --test. Similar to the above, but I think requires
more CLI/config file changes, which I'm not a fan of.
(c) Just ship tests as a second plugin in a second repo, and document how
to install tests. Can then perhaps
My ultimate would be this:
cordova create TestFilePlugin
cd TestFilePlugin
cordova platform add android
cordova plugin add
http://git-wip-us.apache.org/repos/asf/cordova-labs.git#cdvtest:cordova-plugin-test-framework
cordova plugin add ../cordova-plugin-file/
cordova plugin add ../cordova-plugin
-plugin-test-framework
cordova plugin add ../cordova-plugin-file/
cordova plugin add ../cordova-plugin-file/test/
cordova run android --start cdvtests/index.html
Then do this for each plugin, and for each platform
Then do this for all combinations of plugins
...
Note the run --start does
TestFilePlugin
cordova platform add android
cordova plugin add
http://git-wip-us.apache.org/repos/asf/cordova-labs.git#cdvtest:cordova-plugin-test-framework
cordova plugin add ../cordova-plugin-file/
cordova plugin add ../cordova-plugin-file/test/
cordova run android --start cdvtests
On Thu, Jun 19, 2014 at 7:48 PM, Jesse purplecabb...@gmail.com wrote:
My ultimate would be this:
cordova create TestFilePlugin
cd TestFilePlugin
cordova platform add android
cordova plugin add
http://git-wip-us.apache.org/repos/asf/cordova-labs.git#cdvtest:cordova-plugin-test-framework
GitHub user jpuerto opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/71
CB-6928: Add 304 response test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jpuerto/cordova-mobile-spec master
Alternatively
like any help.
-Michal
On Mon, Jun 16, 2014 at 3:25 PM, Marcel Kinard cmarc...@gmail.com wrote:
Hi, after some discussions here with IBM management, we’re going to bring
in a couple extra interns for a week to jumpstart the migration of the
tests out of mobile-spec into the new plugin test
interns for a week to jumpstart the migration of the
tests out of mobile-spec into the new plugin test framework. Staci
Cooper
will be leading this effort, and Martin Gonzalez will be a part of it.
So if you see a bunch of pull requests, this is what it is for. We’ll
get
the interns to submit
:
Hi, after some discussions here with IBM management, we’re going to
bring
in a couple extra interns for a week to jumpstart the migration of the
tests out of mobile-spec into the new plugin test framework. Staci
Cooper
will be leading this effort, and Martin Gonzalez will be a part of it.
So if you
This is the Cordova Plugin Test Framework readme.md, you can catch up with
the functionality by reading some of the content:
Repository:
https://github.com/apache/cordova-labs
Docs:
https://github.com/apache/cordova-labs/blob/master/README.md
https://github.com/apache/cordova-labs/blob/cdvtest
Martin, thanks for posting those links.
And I'll look into the INFRA tickets I need to file to set up a repo for
that plugin, since its ready to come out of labs.
On Tue, Jun 17, 2014 at 2:06 PM, Martin Gonzalez
martin.c.glez.g...@gmail.com wrote:
This is the Cordova Plugin Test Framework
a repo for
that plugin, since its ready to come out of labs.
On Tue, Jun 17, 2014 at 2:06 PM, Martin Gonzalez
martin.c.glez.g...@gmail.com wrote:
This is the Cordova Plugin Test Framework readme.md, you can catch up with
the functionality by reading some of the content:
Repository:
https
of labs.
On Tue, Jun 17, 2014 at 2:06 PM, Martin Gonzalez
martin.c.glez.g...@gmail.com wrote:
This is the Cordova Plugin Test Framework readme.md, you can catch up
with
the functionality by reading some of the content:
Repository:
https://github.com/apache/cordova-labs
Docs:
https
One thing more - it would be great if user could create a test using
test harness app as well. Is it also considered?
Dnia Tue Jun 17 13:27:22 2014 Martin Gonzalez pisze:
It would be a nice to have in the cli, aimed to just setup the right path
in the config.xml, maybe along with an another
At the time I went through my design iterations I just didn't want to
necessarily depend on cordova tooling changes / documentation. In other
words, someone else may have a different strategy for testing..
My personal opinion would be have the test plugin ship with a plugin hook
(those
the test plugin ship with a plugin hook
(those are in, right? or at least on their way), that will automatically
update the start page if you pass a flag to run command. Ie, in an ideal
world: `cordova run --tests` runs a plugin hook passing in --tests flag
which changes the start page, in a way
Hi, after some discussions here with IBM management, we’re going to bring in a
couple extra interns for a week to jumpstart the migration of the tests out of
mobile-spec into the new plugin test framework. Staci Cooper will be leading
this effort, and Martin Gonzalez will be a part of it.
So
to jumpstart the migration of the
tests out of mobile-spec into the new plugin test framework. Staci Cooper
will be leading this effort, and Martin Gonzalez will be a part of it.
So if you see a bunch of pull requests, this is what it is for. We’ll get
the interns to submit an ICLA asap.
...@gmail.com wrote:
Hi, after some discussions here with IBM management, we’re going to bring
in a couple extra interns for a week to jumpstart the migration of the
tests out of mobile-spec into the new plugin test framework. Staci Cooper
will be leading this effort, and Martin Gonzalez
Hello,
My name is Pavan Joshi and I'm currently building applications with Cordova
Currently while working on Mobilespec3.4.0 version I notice that for a
particular version of Android, contacts.spec.21 test case always fails.
This failure is identified only in 4.1.2 Android version, but the same
GitHub user purplecabbage opened a pull request:
https://github.com/apache/cordova-lib/pull/23
CB-6859 Removed all wp7 references, tests still passing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/purplecabbage/cordova-lib
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/23
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
The test is broken and has been for a while,
Introduced by:
https://issues.apache.org/jira/browse/CB-5421
fix:
https://github.com/apache/cordova-lib/pull/8
Please merge...
Doing a ping to see how far behind the list is.
The dev list may be caught up now. I sent it at 9:40am EDT Monday, it arrived
in James’ gmail inbox within a minute or so.
Woohoo!
On May 19, 2014, at 9:40 AM, Marcel Kinard cmarc...@gmail.com wrote:
Doing a ping to see how far behind the list is.
gmail tells me this was sent 7 days ago?
I stopped getting mail again yesterday. Only tiny random messages float
through... I know you guys are talking more than that ;)
On Thu, May 8, 2014 at 10:03 AM, Michal Mocny mmo...@google.com wrote:
7 days ago - finally arrived, congrats
On Thu, May 8, 2014 at 7:03 AM, Michal Mocny mmo...@google.com wrote:
Wow, one day ago from Shaz ... wonder when this will show up ...
@purplecabbage
risingj.com
On Thu, May 15, 2014 at 12:35 PM, Shazron shaz...@gmail.com wrote:
7 days ago - finally arrived, congrats
On Thu, May 8, 2014 at 7:03 AM, Michal Mocny mmo...@google.com wrote:
Heh. 3 hours it says, but I haven't been checking actively tonight. At
least its improving!
On Fri, May 16, 2014 at 6:44 PM, Jesse purplecabb...@gmail.com wrote:
Wow, one day ago from Shaz ... wonder when this will show up ...
@purplecabbage
risingj.com
On Thu, May 15, 2014 at 12:35
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-windows/pull/19
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
https://github.com/apache/cordova-plugin-device-motion/pull/12
https://github.com/apache/cordova-plugin-camera/pull/25
[Release + 3.5.0] Branch Test Tag RC1 for Ubuntu
Key: CB-6594
URL: https
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-windows/pull/19#issuecomment-41599483
The inclusion of 'eval' to load code is problematic.
This pull-request will not be merged. You can close it.
---
If your project is set up for it, you
GitHub user tripodsan opened a pull request:
https://github.com/apache/cordova-osx/pull/8
CB-6516 (re) add missing test harness
- added TestApp
- added some initial test cases
- added bin/tests to execute the tests from the command line
You can merge this pull request
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/58
CB-6466 Created mobile-spec test
Added a test to mobile-spec to check that filetransfer.download()
automatically creates any nonexistent directories.
Associated with
https
Github user tripodsan commented on the pull request:
https://github.com/apache/cordova-osx/pull/8#issuecomment-41448811
thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user tripodsan closed the pull request at:
https://github.com/apache/cordova-osx/pull/8
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Steven wrote:
DAMN YOU ADOBE NET!!! [cid:361@goomoji.gmail]
I can access it on the guest network.
I was able to access it from a cellular network, but I can’t access it from our
corporate network.
I just set up ci.cordova.io to point there!
I'm guessing Adobe/Blackberry Net block it due to the port.
On Wed, Mar 26, 2014 at 11:39 AM, Marcel Kinard cmarc...@gmail.com wrote:
I'm able to see it from the IBM corporate network.
Looks nice. Great work, David!
On Mar 25, 2014, at 11:05
Steven wrote:
I'm guessing Adobe/Blackberry Net block it due to the port.
Seems likely. Is there any reason it can¹t run on a standard port?
not familiar with Buildbot, each phase of the test has a 'stdio'
link that allows you to see any command output from that step. If a step
fails (stopping the build) you can generally just click the link and see
the error messages.
Test results are saved in a couchDB for posterity, but there is no pretty
and Plugman,
You can see/view the build display at:
http://108.170.217.131:8010/waterfall or http://goo.gl/UNijok
For those not familiar with Buildbot, each phase of the test has a 'stdio'
link that allows you to see any command output from that step. If a step
fails (stopping the build) you can
of the test has a
'stdio'
link that allows you to see any command output from that step. If a step
fails (stopping the build) you can generally just click the link and see
the error messages.
Test results are saved in a couchDB for posterity, but there is no pretty
dashboard
://goo.gl/UNijok
For those not familiar with Buildbot, each phase of the test has a
'stdio'
link that allows you to see any command output from that step. If a step
fails (stopping the build) you can generally just click the link and see
the error messages.
Test results are saved
the build display at:
http://108.170.217.131:8010/waterfall or http://goo.gl/UNijok
For those not familiar with Buildbot, each phase of the test has a 'stdio'
link that allows you to see any command output from that step. If a step
fails (stopping the build) you can generally just click
available
for
the community to view. You can see the status of the tests for Android,
iOS, CLI and Plugman,
You can see/view the build display at:
http://108.170.217.131:8010/waterfall or http://goo.gl/UNijok
For those not familiar with Buildbot, each phase of the test has a
'stdio
://108.170.217.131:8010/waterfall or http://goo.gl/UNijok
For those not familiar with Buildbot, each phase of the test has a
'stdio'
link that allows you to see any command output from that step. If a step
fails (stopping the build) you can generally just click the link and see
the error messages.
Test
501 - 600 of 742 matches
Mail list logo
