3.0

213 views
Skip to first unread message

Simon Stewart

unread,
Oct 5, 2016, 1:04:59 PM10/5/16
to selenium-developers
Alright folks,

I just closed the last open issue on GH that's blocking milestone 3.0. I think we should wait until early next week, and then ship 3.0.0. Any complaints or reasons not to?

Simon

David Stark

unread,
Oct 5, 2016, 1:13:14 PM10/5/16
to selenium-...@googlegroups.com

No complaints, just congratulations. :)

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAOrAhYFbaEAhwr%3DaFWS9r%3DnfuJ40xGVC31TbHP5O1TCCdsj%3DUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Alexei Barantsev

unread,
Oct 5, 2016, 2:33:39 PM10/5/16
to selenium-developers
I'm against the release until we have 100% working green CI.

Regards,
--
Alexei Barantsev, Software-Testing.Ru
mailto: bara...@gmail.com
phone: +7 (916) 726-95-55
skype : barancev

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.

ᐧ

alko

unread,
Oct 6, 2016, 5:41:17 AM10/6/16
to Selenium Developers
Hi folks
 
I'm against the release until we have 100% working green CI.

^^^ as much as I would love to see what is going on in 3.0 I couldn't agree with this guy more. If it's red and it shouldn't be then fix it or remove it; let's eat our own dog food people! (Not that the Jenkins for Jenkins wasn't half red last time I checked).

Simon I unfortunately was on the last cut for the conference in London so I won't attend but will be in town to see both conference and non-conference related folks, maybe I will meet you then in person if you aren't too busy (I won't try to convince you about the merits of Maven again I promise ;) )

Tally-ho...

Alex

Simon Stewart

unread,
Oct 6, 2016, 11:56:49 AM10/6/16
to selenium-developers
On Wed, Oct 5, 2016 at 7:33 PM, Alexei Barantsev <bara...@gmail.com> wrote:
I'm against the release until we have 100% working green CI.

CI has been flaky as heck, and it's impossible to nail down all the problems. If you'd like to fix some builds and there are genuine problems, go for it. I could do with a hand.

Simon

Alex Kogon

unread,
Oct 6, 2016, 11:59:28 AM10/6/16
to selenium-...@googlegroups.com
I have no idea what kind of CI you have or what the issues are. I do have a bit of free time at the moment though; if you can point me in the right direction I can take a look?

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAOrAhYHk%3Dh31%3Dcmthgtn3QfQ-2xyrd_Y8iC44ZYh-fFEhp-adA%40mail.gmail.com.

Simon Stewart

unread,
Oct 6, 2016, 12:02:48 PM10/6/16
to selenium-developers
We have a mix of bits and pieces. There are Jenkins builds, which are flaky because paths contain spaces in the names, but can be found at: 


And there are also Travis builds:


Feel free to pitch in on anything :)

Simon

On Thu, Oct 6, 2016 at 4:59 PM, Alex Kogon <alex...@gmail.com> wrote:
I have no idea what kind of CI you have or what the issues are. I do have a bit of free time at the moment though; if you can point me in the right direction I can take a look?
On 6 October 2016 at 17:56, Simon Stewart <simon.m...@gmail.com> wrote:
On Wed, Oct 5, 2016 at 7:33 PM, Alexei Barantsev <bara...@gmail.com> wrote:
I'm against the release until we have 100% working green CI.

CI has been flaky as heck, and it's impossible to nail down all the problems. If you'd like to fix some builds and there are genuine problems, go for it. I could do with a hand.

Simon

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAOrAhYHk%3Dh31%3Dcmthgtn3QfQ-2xyrd_Y8iC44ZYh-fFEhp-adA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CACAhv6%2BuAgGMx1n-vaoe6ey1FiFLKE9Uuzret8NaQF6-PpThRg%40mail.gmail.com.

Alex Kogon

unread,
Oct 6, 2016, 12:09:14 PM10/6/16
to selenium-...@googlegroups.com
Cool I take a look, thanks

On 6 October 2016 at 18:02, Simon Stewart <simon.m...@gmail.com> wrote:
We have a mix of bits and pieces. There are Jenkins builds, which are flaky because paths contain spaces in the names, but can be found at: 


And there are also Travis builds:


Feel free to pitch in on anything :)

Simon
On Thu, Oct 6, 2016 at 4:59 PM, Alex Kogon <alex...@gmail.com> wrote:
I have no idea what kind of CI you have or what the issues are. I do have a bit of free time at the moment though; if you can point me in the right direction I can take a look?

On 6 October 2016 at 17:56, Simon Stewart <simon.m...@gmail.com> wrote:
On Wed, Oct 5, 2016 at 7:33 PM, Alexei Barantsev <bara...@gmail.com> wrote:
I'm against the release until we have 100% working green CI.

CI has been flaky as heck, and it's impossible to nail down all the problems. If you'd like to fix some builds and there are genuine problems, go for it. I could do with a hand.

Simon

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAOrAhYHk%3Dh31%3Dcmthgtn3QfQ-2xyrd_Y8iC44ZYh-fFEhp-adA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsubscribe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CACAhv6%2BuAgGMx1n-vaoe6ey1FiFLKE9Uuzret8NaQF6-PpThRg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAOrAhYFnD7eLE%3Dw7-j6TQFbCB4XF3-%2BpOHqu3QczsK0X8br1fw%40mail.gmail.com.

Aaron Evans

unread,
Oct 6, 2016, 8:02:14 PM10/6/16
to Selenium Developers
I'll pitch in with helping CI.

Aaron Evans

unread,
Oct 6, 2016, 8:04:56 PM10/6/16
to Selenium Developers
Alko, if you take lead I'll help with tasks. First step I guess us to see what's being done and if tests can pass locally.

Guess I need to learn about crazy fun or whatever

Alex Kogon

unread,
Oct 7, 2016, 3:34:56 AM10/7/16
to selenium-...@googlegroups.com
Hi Aaron

I take a look this morning and see what I can find, will be in touch. I'm sure I will have questions quite soon.

Thanks

Alex

On 7 October 2016 at 02:04, Aaron Evans <aar...@one-shore.com> wrote:
Alko, if you take lead I'll help with tasks.  First step I guess us to see what's being done and if tests can pass locally.

Guess I need to learn about crazy fun or whatever
--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/6212f941-b552-4ebf-ba9f-e8f7c892b77a%40googlegroups.com.

Alex Kogon

unread,
Oct 7, 2016, 5:03:26 AM10/7/16
to selenium-...@googlegroups.com
Hi guys,

I'm just trying to understand what I see here...

First question--

I'm assuming these tests which failed in the last day (and haven't passed in 4 months) are where we should focus?

Inline images 1

and these are the builds:

Inline images 3


What's up with these jobs which haven't been run for months (or for one, never)? Should they just be removed?

Inline images 2

Inline images 1

Could we add a build pipeline view to Jenkins to better understand the flow?

Thanks

Alex

On 7 October 2016 at 09:34, Alex Kogon <alex...@gmail.com> wrote:
Hi Aaron

I take a look this morning and see what I can find, will be in touch. I'm sure I will have questions quite soon.

Thanks

Alex
On 7 October 2016 at 02:04, Aaron Evans <aar...@one-shore.com> wrote:
Alko, if you take lead I'll help with tasks.  First step I guess us to see what's being done and if tests can pass locally.

Guess I need to learn about crazy fun or whatever

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.

alko

unread,
Oct 7, 2016, 5:19:13 AM10/7/16
to Selenium Developers
Hi Simon,

Not sure if the missing "pathlib" library is relevant?

Warning raised by BUCK file parser: Traceback (most recent call last):
Warning raised by BUCK file parser:   File "/jenkins/workspace/Firefox 45 Win7 Synthesized Java Tests/selenium-trunk/buck-out/tmp/buck_run.uw4bxU/buck6527850367397704311.py", line 16, in <module>
Warning raised by BUCK file parser:     from pathlib import Path, PureWindowsPath, PurePath
Warning raised by BUCK file parser: ImportError: No module named pathlib
Parse error for build file /jenkins/workspace/Firefox 45 Win7 Synthesized Java Tests/selenium-trunk/javascript/webdriver/BUCK: Parser exited unexpectedly

(from http://ci.seleniumhq.org:8080/job/Firefox_45_Win7_Java_Tests/lastSuccessfulBuild/consoleFull)

I do see the spaces in the path names, these could be escaped or put in quotes perhaps? Or maybe we should refactor it to not have spaces?

Thanks

Alex

On Thursday, 6 October 2016 18:02:48 UTC+2, Simon Stewart wrote:
We have a mix of bits and pieces. There are Jenkins builds, which are flaky because paths contain spaces in the names, but can be found at: 


And there are also Travis builds:


Feel free to pitch in on anything :)

Simon
On Thu, Oct 6, 2016 at 4:59 PM, Alex Kogon <alex...@gmail.com> wrote:
I have no idea what kind of CI you have or what the issues are. I do have a bit of free time at the moment though; if you can point me in the right direction I can take a look?
On 6 October 2016 at 17:56, Simon Stewart <simon.m...@gmail.com> wrote:
On Wed, Oct 5, 2016 at 7:33 PM, Alexei Barantsev <bara...@gmail.com> wrote:
I'm against the release until we have 100% working green CI.

CI has been flaky as heck, and it's impossible to nail down all the problems. If you'd like to fix some builds and there are genuine problems, go for it. I could do with a hand.

Simon

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.

Alex Kogon

unread,
Oct 7, 2016, 5:45:47 AM10/7/16
to selenium-...@googlegroups.com
Hi guys (and gals I hope),

Looks to me like this "Build All Java" http://ci.seleniumhq.org:8080/job/Build_All_Java/ is the root of the Jenkins flows. From the text at the top it assumes that all the binary object code it needs is already compiled (I'll assume for now that this is being handled).

This seems to trigger these projects:
Inline images 1
many of which seem to be disabled from the grey dots visible above, though the log of the build indicates only some of them are (and clicking on them shows that they are disabled but were run yesterday): 

Triggering a new build of Firefox 38 Linux Javascript Tests
Triggering a new build of Small Tests
Triggering a new build of Firefox 38 Linux Synthesized Java Tests
Triggering a new build of Firefox 44 Win7 Synthesized Java Tests
Triggering a new build of Firefox 44 Win7 Javascript Tests
Triggering a new build of Firefox 45 Win7 Javascript Tests
Triggering a new build of Firefox 38 Win7 Synthesized Java Tests
Triggering a new build of build-atoms-chromedriver
Triggering a new build of Firefox 44 Linux Synthesized Java Tests
Triggering a new build of Firefox 44Linux Javascript Tests
Firefox Beta Win7 Synthesized Java Tests is disabled. Triggering skipped
Triggering a new build of Publish test web pages
Triggering a new build of Firefox 45 Linux WDBS Java Tests
Triggering a new build of Firefox 45 Linux Synthesized Java Tests
Triggering a new build of Firefox 38 MacOS Synthesized Java Tests
Triggering a new build of HtmlUnit Java Tests
Triggering a new build of Build_All_BUCK_Linux
Triggering a new build of Firefox 38 Linux WDBS Java Tests
Triggering a new build of Firefox 38 Win7 Javascript Tests
Triggering a new build of Firefox 45 Linux Javascript Tests
Firefox Beta Linux Javascript Tests is disabled. Triggering skipped
Firefox Beta Linux Synthesized Java Tests is disabled. Triggering skipped
Firefox Beta Win7 Javascript Tests is disabled. Triggering skipped
Triggering a new build of Firefox_45_Win7_Synthesized_Java_Tests
Triggering a new build of build-atoms-thirdparty-dependent

I wonder also if these should be run in any particular order; particularly the "Build_All_BUCK_Linux", "build-atoms-*" and "Publish test web pages" jobs may be required before the tests are executed to properly configure the environment (based solely upon their names)? I also found this message in the log which may be related:

Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered


Looking at the log for the latest build (http://ci.seleniumhq.org:8080/job/Build_All_Java/6932/consoleFull) I see this which is generating a 404 response, not sure if that is in any way significant (or if this is a "feature"):

[workspace] $ /bin/sh -xe /tmp/hudson3659823603697034697.sh
+ echo Pinging Jari's dashboard
Pinging Jari's dashboard
+ curl -XPOST -d http://ci.seleniumhq.org:8080/job/Build_All_Java/6932/ http://dashboard.ci.seleniumhq.org/build
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   222  100   168  100    54    565    181 --:--:-- --:--:-- --:--:--   567
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.8.1</center>
</body>
</html>


I also see some jobs seem to be skipped, and there seem to be some classes which are being built multiple times, or namespace collisions (which could be a problem).

Continuing to dig (as much as I can as an anonymous user...)

Tnx

Alex





To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.

Alex Kogon

unread,
Oct 7, 2016, 5:50:28 AM10/7/16
to selenium-...@googlegroups.com
BTW it would be nice to be able to login and at least view the job configurations.

I assume these Jenkins jobs are being manually created/configured and we aren't using something like DotCI (https://www.cloudbees.com/blog/dotci-plugin-providing-new-way-build-jenkins-docker-and-github)?

Alex Kogon

unread,
Oct 7, 2016, 6:03:29 AM10/7/16
to selenium-...@googlegroups.com
Looking at Build_All_BUCK_Linux (http://ci.seleniumhq.org:8080/job/Build_All_BUCK_Linux/615/console), I see that it is deleting its workspace and doing a clean "clone" of the git repo:

Deleting project workspace... done

Cloning the remote Git repository
Cloning repository https://github.com/SeleniumHQ/selenium.git

after the Build_All_Java (http://ci.seleniumhq.org:8080/job/Build_All_Java/6932/consoleFull) job has been run, which appears to not be deleting its workspace but just using Git to get the latest version:

Started by an SCM change
Building on master in workspace /mnt/jenkins/data/jobs/Build_All_Java/workspace
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/SeleniumHQ/selenium.git # timeout=10
Fetching upstream changes from https://github.com/SeleniumHQ/selenium.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress https://github.com/SeleniumHQ/selenium.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision bf47492f6596872f214ded935802ce47c802dcde (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f bf47492f6596872f214ded935802ce47c802dcde
 > git rev-list 30ef76683d75f15c919e10fd4103468594b41a0c # timeout=10
 > git tag -a -f -m Jenkins Build #6932 jenkins-Build_All_Java-6932 # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10

Not quite sure why the second job is doing a delete/clone when the first isn't, or why it isn't using the archived workspace of the first? Seems redundant and inefficient if not actually wrong...

Alex Kogon

unread,
Oct 7, 2016, 6:34:43 AM10/7/16
to selenium-...@googlegroups.com
Getting past the Build_All_BUCK_Linux job, the missing pathlib module indeed seems to be a problem for all these jobs:

whose last run output consistently reads:

Warning raised by BUCK file parser:     import buck
Warning raised by BUCK file parser:   File "/jenkins/workspace/Firefox 38 Linux Javascript Tests/selenium-trunk/buck-out/tmp/buck_run.caOPP6/buck_python_program2213791347110169026/buck.py", line 9, in <module>
Warning raised by BUCK file parser:     from pathlib import Path, PureWindowsPath, PurePath
Warning raised by BUCK file parser: ImportError: No module named pathlib
BUILD FAILED: Parse error for build file /jenkins/workspace/Firefox 38 Linux Javascript Tests/selenium-trunk/java/client/test/org/openqa/selenium/javascript/BUCK: Parser exited unexpectedly
[-] BUILDING...FINISHED 2.9s
go aborted!
Buck build failed


This job seems to run but times out:
STILL RUNNING 135/135 JOBS 7050.1s 1 test targets
STILL RUNNING 135/135 JOBS 7065.1s 1 test targets
Build timed out (after 120 minutes). Marking the build as failed.



This job failed last night because of the missing module, but appears to have been manually run this morning but fails because the environment is not properly configured (btw I assume these time stamps are in Greenwich Mean Time or...?)

.
..
.
ERROR - Cannot read: /mnt/jenkins/data/jobs/Build_All_Java/workspace/selenium-trunk/third_party/js/wgxpath/unionExpr.js

ERROR - Cannot read: /mnt/jenkins/data/jobs/Build_All_Java/workspace/selenium-trunk/third_party/js/wgxpath/userAgent.js

ERROR - Cannot read: /mnt/jenkins/data/jobs/Build_All_Java/workspace/selenium-trunk/third_party/js/wgxpath/wgxpath.js

108 error(s), 0 warning(s)

[-] BUILDING...FINISHED 20.5s [100%]
go aborted!
Buck build failed


This one also failed with the missing module last night but is currently being run and seems to be getting somewhere:


These jobs appear to have not been run since May:



I will get in touch with Alexei who is running jobs now...

Simon Stewart

unread,
Oct 7, 2016, 7:16:36 AM10/7/16
to selenium-developers
Yeah. The missing pathlib is very relevant, and is why the entire build is failing.

Simon

To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/9a34bdb4-d825-4c44-9610-a230dfc0da1f%40googlegroups.com.

Simon Stewart

unread,
Oct 8, 2016, 8:58:30 AM10/8/16
to selenium-developers
Thanks to a huge amount of effort by plenty of people, the travis builds are now all green. Hurrah!

Simon

Sent from my iPhone

Alex Kogon

unread,
Oct 9, 2016, 1:31:48 AM10/9/16
to selenium-...@googlegroups.com
OK, I'm a bit of an old fashioned guy so I'm more Hudson/Jenkins oriented but assuming they are equivalent you don't need my help any more?

Looking forward to seeing what is new in 3.0, I missed the presentation you gave with my Israeli friends unfortunately was not free at the time.

To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/5BB085A1-9F01-4FB1-94B0-ADA72EEBEC36%40gmail.com.

alko

unread,
Oct 10, 2016, 4:04:49 AM10/10/16
to Selenium Developers
Jenkins still looks pretty unhappy but at least Small_Tests seems to pass now. If you guys care, I'm happy to try to help fix. If not, alla prossima!
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.

Simon Stewart

unread,
Oct 10, 2016, 4:20:19 AM10/10/16
to selenium-developers
Luke, Alexei and the Googlers know more about our Jenkins setup than I do. Pinging them :)

Simon

To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/b999211a-c57a-4b3e-b1ec-4db8d5999c8a%40googlegroups.com.

alko

unread,
Oct 14, 2016, 6:05:41 AM10/14/16
to Selenium Developers
Hi folks

I start putting together a new Jenkins config with automation so it will be portable anywhere, I let you know as I make progress.

Thanks

Alex
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.

alko

unread,
Oct 19, 2016, 5:39:12 AM10/19/16
to Selenium Developers
Hi folks, I refactored the Jenkins on a separate Jenkins instance to include only the Java Build_All job and the the tests which successfully run from it (and don't appear to need anything else) and added the Clone Workspace SCM plugin to replace all the custom code to archive and reuse the workspace. You can check it out at http://52.57.139.107:8080/, that URL will probably change at some point as I move it to a cheaper AWS machine that can't run the builds (but can certainly display the information). If you would actually like to see the configurations you can email me for an account.

Unfortunately I can not do any of this on the actual Selenium Jenkins as I don't have the ability to install plugins. I will send Jason Juang an email as well.

There is a bunch of stuff going on in here and there are also what seem to be dependencies on the environment external to what is going on in Jenkins so I just concentrated on the failing tests. It could be that all these jobs publishing information to Google are still necessary or not.

I'm not sure how much appetite there is to get Jenkins working again it seems very little; if this is not the case I am happy to refactor the actual instance, improve parallelization and add the configuration as code in the repo, and either figure out why Sauce Labs is failing or replace it with an independent grid.

Let me know if you still want to salvage Jenkins, other than that I will be working on something else!

Thanks

Alex

alko

unread,
Oct 19, 2016, 5:50:25 AM10/19/16
to Selenium Developers
Here is the plugin I used to replace the custom code doing the same thing...

alko

unread,
Oct 19, 2016, 6:27:06 AM10/19/16
to Selenium Developers
Finally all of the Internet Explorer jobs are failing because of the missing Python library

Warning raised by BUCK file parser:     from pathlib import Path, PureWindowsPath, PurePath
Warning raised by BUCK file parser: ImportError: No module named pathlib

Alexei Barantsev

unread,
Oct 19, 2016, 7:35:45 AM10/19/16
to Selenium Developers
Renamed the jobs to eliminate spaces. The import issue should be fixed now.


среда, 19 октября 2016 г., 13:27:06 UTC+3 пользователь alko написал:

Alex Kogon

unread,
Oct 19, 2016, 10:33:43 AM10/19/16
to selenium-...@googlegroups.com
OK let me see if they run now; I'm not sure if the spaces in the names were causing the problem or the lack of the library but maybe if it is only loaded dynamically when the spaces exist that fixed it.

I launched it again we'll see what happens (it is going now a few minutes so seems happier maybe)...I let you know if that didn't fix it...

If it did that was a no-brainer indeed, I didn't realize a missing library would be fixed by correcting the job name. Thanks!

Alex

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/f9ca3bf9-6399-4a7c-82b8-556b59be58c4%40googlegroups.com.

alko

unread,
Oct 19, 2016, 10:55:39 AM10/19/16
to Selenium Developers
That did seem to fix that error indeed, but now we get this rather nondescript failure, that go (Buck I presume) killed the Java process, with not much more info. I will turn tracing on and run it again...this could mean it ran out of memory I'm not sure

Preparing: //third_party/js/sizzle:sizzle:header as build/third_party/js/sizzle/sizzle.h
Generating header for build/third_party/js/sizzle/sizzle.js
Falling back to cpp/prebuilt/x64/Release/IEDriverServer.exe
Not using buckd because watchman isn't installed.
[-] PARSING BUCK FILES...FINISHED 8.2s [100%]
./go: line 18: 22801 Killed                  java $JAVA_OPTS -jar third_party/jruby/jruby-complete.jar -X-C -S rake $*
Build step 'Execute shell' marked build as failure

Alex Kogon

unread,
Oct 19, 2016, 12:11:16 PM10/19/16
to selenium-...@googlegroups.com
Failed again with the same error; I try it on master and see if it is happier...

To unsubscribe from this group and all its topics, send an email to selenium-developers+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/95e58d57-596c-44f2-ad5d-a1ef4c358cef%40googlegroups.com.

Alex Kogon

unread,
Oct 19, 2016, 12:47:57 PM10/19/16
to selenium-...@googlegroups.com
I think this was an out of memory error indeed and it seems happier on master...but now it is running very long, not sure what is going on in those tests. Let's see if it times out or what happens.

alko

unread,
Oct 24, 2016, 4:17:52 AM10/24/16
to Selenium Developers
Hi folks

I don't know if anyone has looked at the Jenkins or is interested, I am going to turn it off now as I've discovered that AWS runs on Xen and that the work I'm doing doesn't work on Xen so I'm not going to use it any more. I will keep the Jenkins data volume so I can easily start it up again if anyone is interested.

Other than that I wait to see if the project wants to use Jenkins at all any more!

TTFN

Alex
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-developers/jSnbCajyDLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-developers+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages