Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rultor fails to create script.sh with particular character in script #1193

Closed
tannakartikey opened this issue Jul 3, 2017 · 45 comments
Closed

Comments

@tannakartikey
Copy link
Contributor

tannakartikey commented Jul 3, 2017

I have used the command Xvfb :99 & in my .rultor.yml to send the process in the background.
This is the error I am getting because of it:
/home/r/script.sh: line 9: syntax error near unexpected token `;'
Build log: http://www.rultor.com/t/12220-312615627

Rultor converts the command to Xvfb :99 & while parsing YAML to XML which should be the reason of the failure.

@0crat
Copy link
Collaborator

0crat commented Jul 3, 2017

@yegor256 please, pay attention to this issue

@tannakartikey
Copy link
Contributor Author

tannakartikey commented Jul 3, 2017

@yegor256 I have identified the problem.The command Xvfb :99 & was causing the failure.
Should I change the description/title of the issue?

@yegor256
Copy link
Owner

yegor256 commented Jul 3, 2017

@tannakartikey yes, please, change the title and the description

@tannakartikey tannakartikey changed the title Rultor fails with syntax error in script.sh Rultor fails to create script.sh with particular character in script Jul 4, 2017
@0crat
Copy link
Collaborator

0crat commented Nov 1, 2017

Job gh:yegor256/rultor#1193 is in scope.

@0crat
Copy link
Collaborator

0crat commented Nov 16, 2017

Job gh:yegor256/rultor#1193 assigned to @filfreire, please go ahead (policy).

@0crat
Copy link
Collaborator

0crat commented Nov 21, 2017

@filfreire this job was assigned to you 5 days ago. It will be taken away from you soon, unless you close it, see par.8.

@0crat
Copy link
Collaborator

0crat commented Nov 24, 2017

@filfreire this job was assigned to you 8 days ago. It will be taken away from you soon, unless you close it, see par.8.

@0crat
Copy link
Collaborator

0crat commented Nov 26, 2017

@filfreire resigned from gh:yegor256/rultor#1193, please stop working.

@0crat
Copy link
Collaborator

0crat commented Nov 26, 2017

Job gh:yegor256/rultor#1193 assigned to @filfreire, please go ahead (policy).

@0crat
Copy link
Collaborator

0crat commented Dec 6, 2017

Oops! Job gh:yegor256/rultor#1193 is not assigned to anyone.

@0crat
Copy link
Collaborator

0crat commented Dec 6, 2017

There is an unrecoverable failure on my side. Please, submit it here:

java.lang.IllegalArgumentException: Can't process this type of notification: {"title":"#354 ignore @0crat assignments","url":"https://api.github.com/repos/zerocracy/farm/commits/97096402420866657c759a460ed0c282bcb3a555","latest_comment_url":"https://api.github.com/repos/zerocracy/farm/commits/97096402420866657c759a460ed0c282bcb3a555","type":"Commit"}
	at com.zerocracy.radars.github.ReOnComment.react(ReOnComment.java:103)
	at com.zerocracy.radars.github.ReOnReason.react(ReOnReason.java:56)
	at com.zerocracy.radars.github.Reaction$Chain.react(Reaction.java:74)
	at com.zerocracy.radars.github.ReLogged.react(ReLogged.java:55)
	at com.zerocracy.radars.github.RbOnComment.react(RbOnComment.java:60)
	at com.zerocracy.radars.github.RbByActions.react(RbByActions.java:65)
	at com.zerocracy.radars.github.Rebound$Chain.react(Rebound.java:74)
	at com.zerocracy.radars.github.RbSafe.lambda$react$0(RbSafe.java:65)
	at org.cactoos.func.FuncWithFallback.apply(FuncWithFallback.java:299)
	at org.cactoos...

1.0-SNAPSHOT /cc @yegor256

2 similar comments
@0crat
Copy link
Collaborator

0crat commented Dec 6, 2017

There is an unrecoverable failure on my side. Please, submit it here:

java.lang.IllegalArgumentException: Can't process this type of notification: {"title":"#354 ignore @0crat assignments","url":"https://api.github.com/repos/zerocracy/farm/commits/97096402420866657c759a460ed0c282bcb3a555","latest_comment_url":"https://api.github.com/repos/zerocracy/farm/commits/97096402420866657c759a460ed0c282bcb3a555","type":"Commit"}
	at com.zerocracy.radars.github.ReOnComment.react(ReOnComment.java:103)
	at com.zerocracy.radars.github.ReOnReason.react(ReOnReason.java:56)
	at com.zerocracy.radars.github.Reaction$Chain.react(Reaction.java:74)
	at com.zerocracy.radars.github.ReLogged.react(ReLogged.java:55)
	at com.zerocracy.radars.github.RbOnComment.react(RbOnComment.java:60)
	at com.zerocracy.radars.github.RbByActions.react(RbByActions.java:65)
	at com.zerocracy.radars.github.Rebound$Chain.react(Rebound.java:74)
	at com.zerocracy.radars.github.RbSafe.lambda$react$0(RbSafe.java:65)
	at org.cactoos.func.FuncWithFallback.apply(FuncWithFallback.java:299)
	at org.cactoos...

1.0-SNAPSHOT /cc @yegor256

@0crat
Copy link
Collaborator

0crat commented Dec 6, 2017

There is an unrecoverable failure on my side. Please, submit it here:

java.lang.IllegalArgumentException: Can't process this type of notification: {"title":"#354 ignore @0crat assignments","url":"https://api.github.com/repos/zerocracy/farm/commits/97096402420866657c759a460ed0c282bcb3a555","latest_comment_url":"https://api.github.com/repos/zerocracy/farm/commits/97096402420866657c759a460ed0c282bcb3a555","type":"Commit"}
	at com.zerocracy.radars.github.ReOnComment.react(ReOnComment.java:103)
	at com.zerocracy.radars.github.ReOnReason.react(ReOnReason.java:56)
	at com.zerocracy.radars.github.Reaction$Chain.react(Reaction.java:74)
	at com.zerocracy.radars.github.ReLogged.react(ReLogged.java:55)
	at com.zerocracy.radars.github.RbOnComment.react(RbOnComment.java:60)
	at com.zerocracy.radars.github.RbByActions.react(RbByActions.java:65)
	at com.zerocracy.radars.github.Rebound$Chain.react(Rebound.java:74)
	at com.zerocracy.radars.github.RbSafe.lambda$react$0(RbSafe.java:65)
	at org.cactoos.func.FuncWithFallback.apply(FuncWithFallback.java:299)
	at org.cactoos...

1.0-SNAPSHOT /cc @yegor256

@0crat
Copy link
Collaborator

0crat commented Dec 7, 2017

Job gh:yegor256/rultor#1193 assigned to @filfreire, please go ahead (policy).

@paulodamaso
Copy link
Contributor

@rultor status

@rultor
Copy link
Collaborator

rultor commented Jan 2, 2019

@rultor status

@paulodamaso This is what's going on here:

  • no new requests registered
  • build is not running
    []

More information about Rultor commands you can get here.

@paulodamaso
Copy link
Contributor

@0crat status

@0crat
Copy link
Collaborator

0crat commented Jan 2, 2019

@0crat status (here)

@paulodamaso This is what I know about this job in C3SAYRPH9, as in §32:

@0crat
Copy link
Collaborator

0crat commented Jan 2, 2019

@paulodamaso/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@paulodamaso
Copy link
Contributor

@0crat wait for #1286 review

@0crat
Copy link
Collaborator

0crat commented Jan 5, 2019

@0crat wait for #1286 review (here)

@paulodamaso The impediment for #1193 was registered successfully by @paulodamaso/z

@0crat
Copy link
Collaborator

0crat commented Feb 6, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 11, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 16, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 21, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 26, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 3, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 8, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 13, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 18, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 23, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@Glusk
Copy link
Contributor

Glusk commented Oct 20, 2019

Rultor converts the command to Xvfb :99 & while parsing YAML to XML which should be the reason of the failure.

This is not entirely true.

While the XML text content used in a store may be escaped, it is also unescaped when rultor requires it to build the scripts.

Hence the issue is not with the special character &, as there is clearly no & entry in the log reported. Rultor handles the command Xvfb :99 & just fine. The problem must have been somewhere else.

I would love to see the .rultor.yml for this http://www.rultor.com/t/12220-312615627. Where is it @tannakartikey - I can't seem to find it?

@yegor256 Maybe rultor logs should log the commit hash that's currently beinng worked on to help prevent such issue reporting inconveniences?


Update

There seems to be no way of accessing the .rultor.yml that produced the failed build. I propose this issue to be closed and 9dfa19c to be reverted.

@0crat
Copy link
Collaborator

0crat commented Oct 21, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Oct 26, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Oct 31, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 5, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 10, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 15, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 20, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 25, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 30, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Dec 5, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Dec 10, 2019

@yegor256/z everybody who has role DEV is banned at #1193; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256
Copy link
Owner

yegor256 commented Nov 7, 2022

@tannakartikey I believe it's fixed

@yegor256 yegor256 closed this as completed Nov 7, 2022
@0crat
Copy link
Collaborator

0crat commented Nov 7, 2022

Job gh:yegor256/rultor#1193 is not assigned, can't get performer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants