[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title Manuel Recena Soto closed an issue as Fixed Jenkins / JENKINS-31738 Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view Change By: Manuel Recena Soto Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title Raul Arabaolaza commented on JENKINS-31738 Re: Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view Many of the problems are related to jobs not being created or configurations not being saved because of JENKINS-36469 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title Raul Arabaolaza started work on JENKINS-31738 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title Raul Arabaolaza assigned an issue to Raul Arabaolaza Jenkins / JENKINS-31738 Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view Change By: Raul Arabaolaza Assignee: Andres Rodriguez Raul Arabaolaza Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title Raul Arabaolaza commented on JENKINS-31738 Re: Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view The errors seem related to some PO not working properly, for example some jobs not being created or some configuration not being saved I am wondering if some scroll issues may be responsible, something like scrolling down and trying to click a button (like save or ok) that are being rerendered due to the scroll, that would explain the apparently randomicity of this issues and why when you execute manually or step by step on a debugger they work fine. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title
Raul Arabaolaza updated an issue
Jenkins / JENKINS-31738
Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Change By:
Raul Arabaolaza
Comment:
{noformat}Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 380.386 sec <<< FAILURE! - in plugins.PrioritySorterPluginTestmatch_jobs_by_name(plugins.PrioritySorterPluginTest) Time elapsed: 138.362 sec <<< ERROR!org.openqa.selenium.NoSuchElementException: Unable to locate By.xpath: .//input[@type='radio'][./@id = 'hudson.model.FreeStyleProject' or ./@name = 'hudson.model.FreeStyleProject' or ./@value = 'hudson.model.FreeStyleProject' or ./@placeholder = 'hudson.model.FreeStyleProject' or ./@id = //label[contains(normalize-space(.), 'hudson.model.FreeStyleProject')]/@for]| .//label[contains(normalize-space(.), 'hudson.model.FreeStyleProject')]//input[@type='radio']| .//label[contains(normalize-space(.), 'hudson.model.FreeStyleProject')][@class='attach-previous']/preceding-sibling::input[@type='radio'] in http://127.0.0.1:62493/job/low_priority/configure{noformat}This happens sometimes on JobsMixIn.create(), at line 24, I don't understand why is looking in the configure page, the change to configure should happen after the job has been created, and the ok button in theory is only clicked after the job' s type has been clicked.Could it be that this code runs in async mode?? That maybe would explain the failure{noformat}findCaption(type, new Finder() {@Override protected WebElement find(String caption) {try {// Jenkins 2.0 introduced a new "new item" page, which listed// the item types differently and did away with the radio buttons.String normalizedCaption = caption.replace('.', '_');return outer.find(by.css("li." + normalizedCaption));} catch (NoSuchElementException e) {// Jenkins 1.x item type selection was by radio button.return outer.find(by.radioButton(caption));}}}).click();{noformat}
Add Comment
[JIRA] (JENKINS-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title
Raul Arabaolaza commented on JENKINS-31738
Re: Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 380.386 sec <<< FAILURE! - in plugins.PrioritySorterPluginTest
match_jobs_by_name(plugins.PrioritySorterPluginTest) Time elapsed: 138.362 sec <<< ERROR!
org.openqa.selenium.NoSuchElementException: Unable to locate By.xpath: .//input[@type='radio'][./@id = 'hudson.model.FreeStyleProject' or ./@name = 'hudson.model.FreeStyleProject' or ./@value = 'hudson.model.FreeStyleProject' or ./@placeholder = 'hudson.model.FreeStyleProject' or ./@id = //label[contains(normalize-space(.), 'hudson.model.FreeStyleProject')]/@for]| .//label[contains(normalize-space(.), 'hudson.model.FreeStyleProject')]//input[@type='radio']| .//label[contains(normalize-space(.), 'hudson.model.FreeStyleProject')][@class='attach-previous']/preceding-sibling::input[@type='radio'] in http://127.0.0.1:62493/job/low_priority/configure
This happens sometimes on JobsMixIn.create(), at line 24, I don't understand why is looking in the configure page, the change to configure should happen after the job has been created, and the ok button in theory is only clicked after the job' s type has been clicked. Could it be that this code runs in async mode?? That maybe would explain the failure
findCaption(type, new Finder() {
@Override protected WebElement find(String caption) {
try {
// Jenkins 2.0 introduced a new "new item" page, which listed
// the item types differently and did away with the radio buttons.
String normalizedCaption = caption.replace('.', '_');
return outer.find(by.css("li." + normalizedCaption));
} catch (NoSuchElementException e) {
// Jenkins 1.x item type selection was by radio button.
return outer.find(by.radioButton(caption));
}
}
}).click();
Add Comment
