1. "Fixed" bug
- Posted by dcuny Feb 02, 2015
- 1347 views
I submitted a bug report last night. The bug crashed Euphoria hard.
Checking on the status of the bug, I see it listed as "Normal" severity, "Fixed" and assigned to no one.
This has me confused for a number of reasons.
How is this a "Normal" bug, and not "Major"? I don't see any guidelines on how bugs are ranked, but I'd assumed that an error crashes the interpreter to be pretty severe.
What does "Fixed" mean? A single developer reported that they didn't have that issue on their version of Euphoria:
Platform: WinNT, Build: WinXP, Service Pack 2:2 no crash eui or euc must be related to an old bug already fixed?
Apparently this was enough for someone to feel the bug could be closed, despite the latest note indicating that it's a confirmed issue in a recent build:
Confirmed with: $ eui -v Euphoria Interpreter v4.1.0 development 64-bit Linux, Using System Memory Revision Date: 2015-02-02 14:18:53, Id: 6300:57179171dbed
Or maybe it was confirmed as not being a bug... It's open to interpretation.
In any event, if it was fixed, how can I get a copy of the "fixed" version? It still crashes on my machine.
What's going on here? 
- David
2. Re: "Fixed" bug
- Posted by jimcbrown (admin) Feb 02, 2015
- 1349 views
I submitted a bug report last night. The bug crashed Euphoria hard.
Thank you for doing this. Getting these tickets filed is one of the more troublesome tasks imvho.
Checking on the status of the bug, I see it listed as "Normal" severity, "Fixed" and assigned to no one.
This has me confused for a number of reasons.
How is this a "Normal" bug, and not "Major"? I don't see any guidelines on how bugs are ranked, but I'd assumed that an error crashes the interpreter to be pretty severe.
The ticket form just defaults to normal. I'd argue that such a severe bug should actually be Blocking, though others might have different opinions. Anyways, as the original ticket submitter, you should be able to update the severity status to what you think is appropriate.
What does "Fixed" mean? A single developer reported that they didn't have that issue on their version of Euphoria:
Platform: WinNT, Build: WinXP, Service Pack 2:2 no crash eui or euc must be related to an old bug already fixed?
Apparently this was enough for someone to feel the bug could be closed, despite the latest note indicating that it's a confirmed issue in a recent build:
Confirmed with: $ eui -v Euphoria Interpreter v4.1.0 development 64-bit Linux, Using System Memory Revision Date: 2015-02-02 14:18:53, Id: 6300:57179171dbed
Matt was very ambiguous with what he wrote. I interpreted this to mean that he confirmed that it was fixed, not that it's confirmed as still an issue - especially as it looks like Matt was the one who marked the ticket as fixed.
And if it was fixed, how can I get a copy of the "fixed" version? It still crashes on my machine.
What's going on here?
- David
Unless ne1uno or someone else can provide you with their binary, you'd have to installl the MinGW compiler and build your own version from source.
One of the long term tasks is to get a build server set up so binaries will be produced automatically on a daily basis. This way you could just download the latest binary, build from today's source. We used to have this, but currently lack one.
3. Re: "Fixed" bug
- Posted by ne1uno Feb 02, 2015
- 1296 views
I submitted a bug report last night. The bug crashed Euphoria hard.
Thank you for doing this. Getting these tickets filed is one of the more troublesome tasks imvho.
Checking on the status of the bug, I see it listed as "Normal" severity, "Fixed" and assigned to no one.
This has me confused for a number of reasons.
How is this a "Normal" bug, and not "Major"? I don't see any guidelines on how bugs are ranked, but I'd assumed that an error crashes the interpreter to be pretty severe.
The ticket form just defaults to normal. I'd argue that such a severe bug should actually be Blocking, though others might have different opinions. Anyways, as the original ticket submitter, you should be able to update the severity status to what you think is appropriate.
What does "Fixed" mean? A single developer reported that they didn't have that issue on their version of Euphoria:
Platform: WinNT, Build: WinXP, Service Pack 2:2 no crash eui or euc must be related to an old bug already fixed?
Apparently this was enough for someone to feel the bug could be closed, despite the latest note indicating that it's a confirmed issue in a recent build:
Confirmed with: $ eui -v Euphoria Interpreter v4.1.0 development 64-bit Linux, Using System Memory Revision Date: 2015-02-02 14:18:53, Id: 6300:57179171dbed
Matt was very ambiguous with what he wrote. I interpreted this to mean that he confirmed that it was fixed, not that it's confirmed as still an issue - especially as it looks like Matt was the one who marked the ticket as fixed.
And if it was fixed, how can I get a copy of the "fixed" version? It still crashes on my machine.
What's going on here?
- David
Unless ne1uno or someone else can provide you with their binary, you'd have to installl the MinGW compiler and build your own version from source.
One of the long term tasks is to get a build server set up so binaries will be produced automatically on a daily basis. This way you could just download the latest binary, build from today's source. We used to have this, but currently lack one.
I don't have a 64 bit system. I also assumed Matt tested the code on 64 bit and marked the ticket fixed. invalid or duplicate would work too.
I marked the bug down to normal. if you mark everything severe and blocking it's impossible to prioritize. let the person assigned the bug decide.
there has always been a missing status change note that the ticket system should add, as do most other bug trackers. anyone with access could set any change with no obvious trail.
Matt also fixed a different bug than the one I commented on.
too bad source forge and amazon no longer give build farm access.
is there any chance of a weekly or monthly eubin build of a few OS and branches that have had commits? with test report. I know at one point the cross compiler failed and or the build was taking too much CPU but is that not an easy upgrade/throttle option? (assuming one had the time & skills)
4. Re: "Fixed" bug
- Posted by dcuny Feb 02, 2015
- 1308 views
Thanks for the prompt response!
The ticket form just defaults to normal.
I thought I set it as severe, so that's why I raised the question. I was under the impression that someone changed it.
Part of my confusion is that I can't see who made changes to the ticket values. That's why I wrote "apparently" - it's not clear looking at the ticket who took what action.
I don't know if that sort information is available, but it's a nice feature if you've got it.
Matt was very ambiguous with what he wrote.
Yes. As I said, I haven't figured out how to see who did what, and that's part of my confusion.
Unless ne1uno or someone else can provide you with their binary, you'd have to installl the MinGW compiler and build your own version from source.
This is my key point. As a user, until I get a fixed version of Euphoria, it means I still have a fatal, non-fixed bug on my machine.
Users to compile Euphoria on their own is obviously less than optimal. I can't speak for other users, but one reason I chose to try Euphoria interpreter was to get away from having to use a C compiler.
Plus, I'm still not sure where to get the most current source from.
- David
5. Re: "Fixed" bug
- Posted by dcuny Feb 02, 2015
- 1295 views
I marked the bug down to normal. if you mark everything severe and blocking it's impossible to prioritize. let the person assigned the bug decide.
So... a critical bug was reported as such (it literally crashed Euphoria), marked down to "Normal" for reasons that had nothing to do with the actual severity, and apparently never assigned to anyone to verify?
And there's no way to use the bug tracker to verify what happened?
I'm obviously suggesting that this is bad. 
there has always been a missing status change note that the ticket system should add, as do most other bug trackers. anyone with access could set any change with no obvious trail.
Yes, I'm surprised it's not there too. It's really useful.
too bad source forge and amazon no longer give build farm access.
I assume it takes hours to build Euphoria and run the tests?
- David
6. Re: "Fixed" bug
- Posted by ryanj Feb 02, 2015
- 1303 views
One of the long term tasks is to get a build server set up so binaries will be produced automatically on a daily basis. This way you could just download the latest binary, build from today's source. We used to have this, but currently lack one.
I am thinking about getting a VPS soon. If i do, i might be willing to provide a user account for automated builds. What resources would be required?
